Microsoft Viva Glint
Visier can retrieve data through this connector if the following requirements are met.
The Microsoft Viva Glint data connector retrieves raw survey response data.
Note: This connector relies on the Microsoft Graph Rest APIs in the beta endpoint. Because these APIs are in preview, they are subject to change by Microsoft without notice, which may cause unexpected breaking changes.
Prerequisites
- Register a client application in Microsoft Entra ID.
- Allow network and data traffic between Visier and your source system. For more information, see Allow Visier Connections.
Client application
Register an application in Microsoft Entra ID and grant the appropriate data access permissions so that Visier can retrieve your source data.
Register a client application in Microsoft Entra ID
Note: Due to the highly sensitive nature of Viva Glint survey data, application permissions must be approved by your tenant's Global Administrator.
- Sign in to the Microsoft Azure Portal or Microsoft Entra Admin Center as a Global Administrator.
- Go to Microsoft Entra ID > App registrations.
- Click New registration.
- Enter the following configuration details:
- Name: Enter a clear, meaningful name for the client application, such as
Visier-VivaGlint-Connector. - Supported account types: Select one of the following:
- Single Tenant if the API will be accessed solely within this tenant.
- Multi-tenant if your corporate framework requires cross-tenant access.
- Redirect URI (Optional): The specific destination where the authentication server sends users after they successfully log in or authorize an application.
- Name: Enter a clear, meaningful name for the client application, such as
- Click Register.
- Copy the Application (Client) ID and Directory (Tenant) ID from the Application Overview page, as you will need to provide the credentials in Visier.
Generate a client secret
To authenticate the connection between your registered application and Visier, you must provide a client secret.
- In your registered client application, go to Manage > Certificates & secrets.
- In the Client secrets tab, click New client secret.
- Enter the following configuration details:
- Description: Enter a clear, meaningful description such as,
Visier Glint Export Secret. - Expiration: Select an expiration timeframe aligned with your organization's security policy.
- Description: Enter a clear, meaningful description such as,
- Click Add.
- Copy and store the generated client secret in a secure location before leaving this page. Once you leave, the client secret will be permanently masked and cannot be viewed again. You will need to provide the credentials in Visier.
Configure Microsoft Graph API permissions
To extract data from Viva Glint, you must assign the required permission scope to your registered application.
- In your registered client application, go to Manage > API permissions.
- Click Add a permission.
- Click Microsoft APIs > Microsoft Graph.
- Select Application permissions as the connector runs as a background service without a signed-in user.
- Locate the SentimentSurvey.Export.All scope by searching for
Export. The target scope allows the app to export Viva Glint data for the tenant. - Select the SentimentSurvey.Export.All scope and click Add permissions.
Grant admin consent
Permissions will not be active until admin consent is explicitly granted on the tenant level. Without admin consent, you may be able to generate an access token. However, any subsequent API requests to extract data will fail immediately with a 403 Forbidden error.
-
In API permissions, click Grant admin consent for TenantName and select Yes to confirm.
Result: The Status column for the permission changes to Granted with a green checkmark.
Retrieve Client UUID
To route data extraction requests to the correct environment, you will need to provide your organization's unique Viva Glint identifier in Visier.
- Sign in to your Microsoft Viva Glint platform as an administrator.
- Go to General settings from your admin dashboard or configuration menu.
- In the navigation menu, click Company Information under All Settings.
- Copy the Client UUID. You will need to provide the credentials in Visier.
Connector credentials
Create a connector credential in Visier to authenticate and authorize access to your source system. Connector credentials can be created in Studio or through an API. For more information, see Set Up Data Connectors and "Create a connector credential" in API Reference. You will need to provide the following credentials in your connector credential configuration.
|
Credential |
Description |
Example |
|---|---|---|
|
Directory (Tenant) ID |
The unique identifier of your Glint tenant. |
a1b2c3d4-e5f6-7a8b-9c0d-1e2f3a4b5c6d |
|
Application (Client) ID |
The unique identifier of the client application client you created. |
f8e7d6c5-b4a3-2f1e-0d9c-8b7a6f5e4d3c |
|
Client Secret |
The client secret of the client application you created. |
R2t7Y~bNWkHGClSd8rcDVKbMPtzQAJnKkWfXbMs |
|
Client Name / Client UUID |
The unique identifier of your Glint experience. |
visierglintcustomer |
Data files
The connector retrieves survey response data and outputs a single subject: SurveyResponse. A single source is created that contains all available surveys and the survey data is mapped to the Employee_Survey analytic object.
The generated Glint template automatically maps survey data into Visier's Employee_Survey analytic model.
The connector transforms Viva Glint's native wide-format CSV files, where each survey question is represented as a separate column, into a schema with one row for each respondent–question pair. The resulting schema contains 16 fixed columns: 11 identity columns and 5 question columns.
Identity columns
- Survey Cycle Creation Date
- Survey Cycle Completion Date
- Survey Cycle Title
- Survey Cycle UUID
- Survey UUID
- First Name
- Last Name
- Status
- Employee ID
- Manager ID
Question columns
- Question
- Response
- Comment
- Comment Topics
- Sensitive Comment Flag
Data extraction and ingestion
Once the credentials are saved in Visier, the data connector communicates with Microsoft Graph using an asynchronous, multi-stage ingestion workflow.
Export Job Initiation
The connector initiates an export operation by targeting your client experience ID and submitting an optional ISO-formatted data window (startDateTime to endDateTime).
Status Polling
The connector continuously checks the background extraction job status. It tracks the process through various operational states, moving from Queued or In Progress until it hits Succeeded.
Payload Retrieval
Once the export job has completed successfully, the connector downloads the compressed raw survey binary file (CSV or JSON format) directly into the platform.
Batch Size Override
The Batch Size Override controls how many months of survey data are requested in each exportSurvey API call. By default, the connector retrieves data in 6-month windows. You can specify a smaller value to reduce the size of each request. The maximum supported value is 6 months. Values greater than 6 are automatically capped to comply with the API limit.
How the connector loads data
Initially, data connectors retrieve a full history for each subject to generate an initial history of events. In each subsequent data retrieval, each connector handles the data load differently.
- Full load: All data from the source system is loaded into Visier.
- Delta load: Only changed data is loaded into Visier. A delta load may take either the entire history or a specific number of years of history for each changed record.
- Snapshot load: All data at a particular point in time. A snapshot load does not contain historical records or show changes over time.
- Partial load: A subset of data is loaded into Visier.
After the initial load, this connector retrieves only records that have changed or surveys that have been closed since the last extraction date. In-progress surveys are skipped until they are completed, at which point the connector retrieves the complete data set.
